This is still in draft state. What it does so far: upon receiving SIGUSR2, it will increase the global counter, thus causing a reload of all certificate scopes next time they are needed.

I confirmed that it works by changing the file and invoking

docker compose kill -s SIGUSR2 web

However, if the file cannot be loaded (because of syntax errors, for instance), the error will only appear later on (as I said, the next time the certificate scopes are needed). I want to see the error at once. For this and other reasons, I still want to implement the following changes

• load the scope files at once
• either share the precomputed values across threads (because they are read only) or compute them from pre-loaded spec files
• also reload bootstrap.yaml
• (maybe?) no longer keep account data in the database, but use the same technique as for the scopes?

Oh, and

• the templates must be reloaded as well

@martinmo It's now based on #751 to remove the subject parts, so maybe merge that one first.

Your remarks regarding multiprocessing are correct, and I added a note. We would have to change a few things anyway, and frankly, this is a problem for the far future.